Skip to content

Add support to StartTLS on Quota's mailing#4573

Merged
DaanHoogland merged 1 commit into
apache:masterfrom
GutoVeronezi:add-support-to-starttls
Apr 13, 2021
Merged

Add support to StartTLS on Quota's mailing#4573
DaanHoogland merged 1 commit into
apache:masterfrom
GutoVeronezi:add-support-to-starttls

Conversation

@GutoVeronezi

Copy link
Copy Markdown
Contributor

Description

On Quota's mailing settings, ACS has a configuration (quota.usage.smtp.useAuth) to inform if it will use secure SMTP authentication when sending emails.
However, this configuration only refers to use SSL or not. Operators haves no option to choose if they want to use StartTLS.

This PR intends to add support to StartTLS on Quota's mailing settings.

It is interesting to highlight that this enhancement would be able to solve issue #2625 (if it was applied in that setting as well); however, to reduce the scope of change, this one focuses only on Quota's mailing configuration.

Types of changes

  • Breaking change (fix or feature that would cause existing functionality to change)
  • New feature (non-breaking change which adds functionality)
  • Bug fix (non-breaking change which fixes an issue)
  • Enhancement (improves an existing feature and functionality)
  • Cleanup (Code refactoring and cleanup, that may add test cases)

Feature/Enhancement Scale or Bug Severity

Feature/Enhancement Scale

  • Major
  • Minor

How Has This Been Tested?

It has been tested locally on a test lab.

  1. I had Enabled Quota's plugin on the management server and configured it to use Gmail's SMTP server.
server address: smtp.gmail.com
username: gmail address
password: gmail password
port (TLS): 587
  1. On Quota - All Accounts, I added 10 credits to my user and set 20 as min balance.

  2. I had added an gmail address to Accounts > <account> > Users - Email.

  3. I allowed Less secure app access on my Google account.

  4. I had restarted management server.

  5. And I called quota update API via Cloudmonkey. Without the new option being introduced here, I would see an error in the management server. After setting it, everything is fine, and the alert email is sent.

@DaanHoogland DaanHoogland left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

code looks ok, and old behaviour is default, so looks good in that aspect. As a thunderbird user i have the experience that the client can discover what kind of security is used however, can we implement such a thing as well?

@DaanHoogland DaanHoogland added this to the 4.16.0.0 milestone Jan 18, 2021

@RodrigoDLopez RodrigoDLopez left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code LGTM

@yadvr

yadvr commented Feb 12, 2021

Copy link
Copy Markdown
Member

@blueorangutan package

@blueorangutan

Copy link
Copy Markdown

@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

@blueorangutan

Copy link
Copy Markdown

Packaging result: ✖centos7 ✖centos8 ✖debian. JID-2681

@DaanHoogland

Copy link
Copy Markdown
Contributor

@blueorangutan package

@blueorangutan

Copy link
Copy Markdown

@DaanHoogland a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

@blueorangutan

Copy link
Copy Markdown

Packaging result: ✔centos7 ✔centos8 ✖debian. JID-2701

@yadvr

yadvr commented Feb 19, 2021

Copy link
Copy Markdown
Member

@blueorangutan package

@blueorangutan

Copy link
Copy Markdown

@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

1 similar comment
@blueorangutan

Copy link
Copy Markdown

@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

@blueorangutan

Copy link
Copy Markdown

Packaging result: ✔centos7 ✖centos8 ✖debian. JID-2756

@blueorangutan

Copy link
Copy Markdown

Packaging result: ✔centos7 ✖centos8 ✖debian. JID-2757

@GutoVeronezi GutoVeronezi force-pushed the add-support-to-starttls branch from 43b3d7c to 2109523 Compare February 24, 2021 12:00
@GutoVeronezi GutoVeronezi force-pushed the add-support-to-starttls branch from 2109523 to e08ef1a Compare February 24, 2021 12:10
@yadvr

yadvr commented Mar 6, 2021

Copy link
Copy Markdown
Member

@blueorangutan package

@blueorangutan

Copy link
Copy Markdown

@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

@blueorangutan

Copy link
Copy Markdown

Packaging result: ✖centos7 ✖centos8 ✖debian. JID-2878

@yadvr yadvr closed this Apr 5, 2021
@yadvr yadvr reopened this Apr 5, 2021
@yadvr

yadvr commented Apr 5, 2021

Copy link
Copy Markdown
Member

@blueorangutan package

@blueorangutan

Copy link
Copy Markdown

@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

@blueorangutan

Copy link
Copy Markdown

Packaging result: ✔️ centos7 ✔️ centos8 ✔️ debian. SL-JID 325

@GutoVeronezi

Copy link
Copy Markdown
Contributor Author

@rhtyd @DaanHoogland is there anything else to do?

@blueorangutan

Copy link
Copy Markdown

Trillian test result (tid-390)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 42094 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr4573-t390-kvm-centos7.zip
Intermittent failure detected: /marvin/tests/smoke/test_kubernetes_clusters.py
Intermittent failure detected: /marvin/tests/smoke/test_vm_life_cycle.py
Smoke tests completed. 85 look OK, 2 have error(s)
Only failed tests results shown below:

Test Result Time (s) Test File
test_01_deploy_kubernetes_cluster Failure 3609.16 test_kubernetes_clusters.py
test_02_invalid_upgrade_kubernetes_cluster Failure 3602.74 test_kubernetes_clusters.py
test_03_deploy_and_upgrade_kubernetes_cluster Failure 0.05 test_kubernetes_clusters.py
test_04_deploy_and_scale_kubernetes_cluster Failure 0.04 test_kubernetes_clusters.py
test_05_delete_kubernetes_cluster Failure 0.05 test_kubernetes_clusters.py
test_07_deploy_kubernetes_ha_cluster Failure 0.05 test_kubernetes_clusters.py
test_08_deploy_and_upgrade_kubernetes_ha_cluster Failure 0.04 test_kubernetes_clusters.py
test_09_delete_kubernetes_ha_cluster Failure 0.04 test_kubernetes_clusters.py
ContextSuite context=TestKubernetesCluster>:teardown Error 44.66 test_kubernetes_clusters.py
test_01_migrate_VM_and_root_volume Error 71.50 test_vm_life_cycle.py
test_02_migrate_VM_with_two_data_disks Error 53.28 test_vm_life_cycle.py

@DaanHoogland DaanHoogland merged commit b28d638 into apache:master Apr 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants